5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

Specifying Constant Values


You can use constant values in certain ILF statements where a field name is allowed. You leave the application ID blank when specifying a constant value. Because there are different types of fields included within an APPX application, you need to understand exactly how to specify each data type as a constant value.

APPX stores or communicates data in any of three formats, and automatically translates between these formats as appropriate. The three data representations are:

The external or display format communicates data to an application user. This format includes characters such as $, -, and #, which often provide a more meaningful presentation to a user.

The internal or stored format allows APPX to store and manage data in a specified (and usually optimum) manner. For example, you may choose to store a numeric money field in packed decimal format.

The universal format allows you to reference a field within the context of ILF statements, regardless of how the data is stored or displayed.

Use the universal format to specify constants as fields within statements.

Application Design Manual                                         "Powered by Appx Software"

557

©2006 By APPX Software, Inc. All Rights Reserved